-
Notifications
You must be signed in to change notification settings - Fork 97
Create 2018-08-20--go-core-dev-team-weekly.md #683
Conversation
@@ -0,0 +1,204 @@ | |||
# 💫Golang Core Dev Team Weekly Sync 🙌🏽 August 20, 2018 | |||
|
|||
- **Lead:** Dominic Della Valle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@djdv thank you for hosting ❤️
|
||
- **Lead:** Dominic Della Valle | ||
- **Notetaker:** | ||
- @bigs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bigs thank you for notetaking 🌟
- @kevina | ||
- @hsanjuan | ||
- @Magik6k | ||
- **Recording:** _add link to recording once it's online_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note, we need to say that the recording is private to the Go Core Dev Team
- Refined the IPFS on fuse implementation | ||
- Added caching around things like pins, keys, and metadata | ||
- Reduced lock contention | ||
- Reworked how indexes are generated and referenced |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@djdv Can you do a demo of it working on Windows? @hacdias will be excited about it for IPFS Desktop for sure and @alanshaw will be able to give it a new spin with https://www.npmjs.com/package/ipfs-fuse
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have an informal demo of the original implementation here: ipfs/kubo#5003 (comment)
The refinement is the same, just much faster.
I plan to do a proper demo when this is closer to completion (still working on write support).
- This was resolved while refactoring | ||
- Currently I'm dealing with an issue related to file ownership | ||
- I am currently in contact with the cgofuse developer about it | ||
- Currently working around this by setting everything to 0777, later node owners will be the same as the process owner/invoker |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@djdv anything that anyone in the Go Core Dev Team or PL can do to help here or is this under your control? Just let me know :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Things should be good for the moment ;^)
|
||
@kevina | ||
- Done: | ||
- In Progress: Begin new "cid" sub-command https://github.com/ipfs/go-ipfs/pull/5385 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kevina Is this for CIDv0 to CIDv1 migration? Please create an issue on http://github.com/ipfs/specs so that the other IPFS implementations and Client libraries can keep up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was something that I consider go specific and something I want to put into a spec. One of the things it does is to provide a way to convert CIDs to base32 CIDv1. I considered making it a separate utility but that will be a separate binary that might not be installed. If it was part of go-ipfs
it is nearly guaranteed to be available when if its a separate utility
- multistream-select (again) | ||
- continue work on IPLD interfaces/migration. | ||
- Blocked: | ||
- @daviddias: [Remove bitswap unwant](https://github.com/ipfs/go-ipfs/pull/5308) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Followed up, here ipfs/kubo#5308 (comment)
- continue work on IPLD interfaces/migration. | ||
- Blocked: | ||
- @daviddias: [Remove bitswap unwant](https://github.com/ipfs/go-ipfs/pull/5308) | ||
- @daviddias: [New multiaddr protocol](https://github.com/multiformats/multiaddr/pull/68) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've followed up. Feel that I need to do lot more reading before signing off such a thing (lot's of RFCs to read and context to absorb) and unfortunately I've very limited time right now to go that deep exploring.
Can you give me a date in which this becomes critical to not be solved? Or, better, can do you a 5 minute presentation with your brain dump?
- @daviddias: [Remove bitswap unwant](https://github.com/ipfs/go-ipfs/pull/5308) | ||
- @daviddias: [New multiaddr protocol](https://github.com/multiformats/multiaddr/pull/68) | ||
- Ask: | ||
- Please review PRs! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which ones?
- Blocked: | ||
- Next: | ||
|
||
@bigs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bigs, Did you get to meet with @jacobheun and @travisperson? Ref https://github.com/ipfs/pm/pull/678/files#r210003491
- Waffle cleanup | ||
- Continue developing go/js/rust interop demo | ||
- Docs improvement SOW and interviews | ||
- Rust dev shop SOWs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mgoelzer I don't have any particular thing against sharing this kind of update here, but have in mind that this is a call focused for Dev of the Go implementations of IPFS, libp2p and IPLD and not for PM'ing or Protocol Labs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 - noted for future ref
No description provided.